System and method for collecting whole blood from blood donors

ABSTRACT

A system and method for collecting whole blood from blood donors includes first and second whole blood collection devices disposed at different blood donation centers. A remote server computer is in communication with the blood collection devices. The whole blood collection devices transfer donation procedure information to the remote server. The remote server computer facilitates retrieval of the donation procedure information at a handheld computing device. The donation procedure information includes data based on product volume collected and data indicating performance of operators of the whole blood collection devices. The handheld computing device displays a number of whole blood units collected. Blood collection can be improved using the donation procedure information.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of prior application Ser. No.17/732,073, filed Apr. 28, 2022, which is a continuation of priorapplication Ser. No. 15/641,917, filed Jul. 5, 2017, which is acontinuation of prior application Ser. No. 14/971,707, filed Dec. 16,2015 and issued as U.S. Pat. No. 9,727,696, which is a continuation ofprior application Ser. No. 13/209,161, filed on Aug. 12, 2011, whichclaims the benefit of U.S. Provisional App. No. 61/373,197, filed onAug. 12, 2010, and U.S. Provisional App. No. 61/383,174, filed on Sep.15, 2010, all of which are herein incorporated by reference in theirentireties. Application Ser. No. 14/971,707 is a continuation-in-part ofprior application Ser. No. 13/748,580, filed on Jan. 23, 2013, whichclaims the benefit of U.S. Provisional App. No. 61/589,755, filed onJan. 23, 2012 and U.S. Provisional App. No. 61/637,694, filed on Apr.24, 2012, all of which are expressly incorporated by reference herein intheir entireties. The present application is related to priorapplication Ser. No. 13/209,151, filed Aug. 12, 2011 and issued as U.S.Pat. No. 8,676,600 and prior application Ser. No. 13/209,163, filed Aug.12, 2011 and issued as U.S. Pat. No. 8,485,828, both of which areexpressly incorporated by reference herein in their entireties.

FIELD

The present invention relates generally to methods, systems, andapparatus to provide mobile applications for donors, blood centers, andassociated medical personnel.

BACKGROUND

Hospitals, clinics, and other healthcare providers continually face aneed for donated blood to help in treating patients. It is oftendifficult to notify and educate the public regarding donations. Donorsmay not become repeat donors due to a lack of information and access.Operators and administrators may introduce inefficiencies in theiroperation and management of blood collection instruments due to a lackof information and access.

BRIEF SUMMARY

Certain examples provide systems, methods, and apparatus to provideinformation regarding blood collection instruments via a mobile device.

Certain examples provide a computer-implemented method for bloodcollection instrument management. The method includes providing agraphical representation of one or more blood collection instrumentswith a visual indication of a status for each instrument. The graphicalrepresentation is to visually convey information regarding each of theone or more blood collection instruments and is selectable by a user toprovide additional information regarding each of the one or more bloodcollection instruments. The method includes facilitating access totroubleshoot and interact with the one or more blood collectioninstruments via the mobile device. The method includes dynamicallyupdating the status for each instrument via communication between themobile device and one or more blood collection facilities at which theone or more blood collection instruments are located.

Certain examples provide a tangible computer readable storage mediumincluding program code for execution by a processor, the program code,when executed, to implement a method for blood collection instrumentmanagement. The method includes providing a graphical representation ofone or more blood collection instruments with a visual indication of astatus for each instrument. The graphical representation is to visuallyconvey information regarding each of the one or more blood collectioninstruments and is selectable by a user to provide additionalinformation regarding each of the one or more blood collectioninstruments. The method includes facilitating access to troubleshoot andinteract with the one or more blood collection instruments via themobile device. The method includes dynamically updating the status foreach instrument via communication between the mobile device and one ormore blood collection facilities at which the one or more bloodcollection instruments are located.

Certain examples provide a mobile blood collection instrument managementsystem. The system includes a processor and memory storing instructionsto display content and accept user input to implement, via a mobiledevice: a graphical representation of one or more blood collectioninstruments including a visual indication of a status for eachinstrument, the graphical representation to visually convey informationregarding each of the one or more blood collection instruments andselectable by a user to provide additional information regarding each ofthe one or more blood collection instruments; and an executableapplication to provide access to troubleshoot and interact with the oneor more blood collection instruments via a mobile device. The system isto dynamically update the status for each instrument via communicationbetween the mobile device and one or more blood collection facilities atwhich the one or more blood collection instruments are located.

Certain examples provide a computer-implemented method for bloodcomponent tracking device. The method includes facilitating input of adonor identifier and a collection time for a collected blood componentvia a mobile device. The method includes recording an identifierassociated with a container to transport the collected blood componentfor processing. The method includes tracking the container with thecollected blood component via the mobile device affixed to the containerduring transit. The method includes providing the donor identifier,container identifier, collection time, and tracking information to acomputer at a collection center for processing of the collected bloodcomponent.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIGS. 1-5 show example interfaces for current and/or potential blooddonors.

FIGS. 6-8 show example interfaces for blood collection device operators.

FIGS. 9-11 illustrate example interfaces for blood centeradministrators.

FIG. 12 illustrates an example mobile device including a donorapplication showing a user's distance from a blood donation center.

FIG. 13 shows an example information screen for a donor application.

FIG. 14 illustrates an example graphic showing visual progress as acollection total approaches a target collection goal.

FIG. 15 depicts example donation update graphics.

FIG. 16 depicts an example histogram that can be displayed via aninformation screen.

FIGS. 17-19 depict example screen shots of a mobile device running anapplication that increases donor awareness.

FIG. 20 depicts an example flowchart for a blood donor application.

FIG. 21 depicts an example mobile device including an interface listingone or more blood collection/processing instruments under control of theoperator.

FIGS. 22-24 provide flow diagrams for methods for donors, operators, andadministrators to review and manage blood collection and associatedinstrument information.

FIG. 25 depicts an example process flow demonstrating how blood productscan be processed and labeled with new product codes.

FIG. 26 is a block diagram of an example system or mobile device.

FIG. 27 is a block diagram of an example processor system that can beused to pump, implement, control and/or drive the systems and methodsdescribed herein.

The foregoing summary, as well as the following detailed description ofcertain embodiments of the present invention, will be better understoodwhen read in conjunction with the appended drawings. For the purpose ofillustrating the invention, certain embodiments are shown in thedrawings. It should be understood, however, that the present inventionis not limited to the arrangements and instrumentality shown in theattached drawings.

DESCRIPTION OF CERTAIN EXAMPLES

Certain examples are shown in the above-identified figures and describedin detail below. In describing these examples, like or identicalreference numbers are used to identify the same or similar elements. Thefigures are not necessarily to scale and certain features and certainviews of the figures may be shown exaggerated in scale or in schematicfor clarity and/or conciseness. Additionally, several examples have beendescribed throughout this specification. Any features from any examplemay be included with, a replacement for, or otherwise combined withother features from other examples.

It will be understood that the present invention may be embodied inother specific forms without departing from the spirit thereof. Thepresent examples and embodiments, therefore, are to be considered in allrespects as illustrative and not restrictive, and the invention is notto be limited to the details presented herein.

Although the following discloses example methods, apparatus, systems,and articles of manufacture including, among other components, firmwareand/or software executed on hardware, it should be noted that suchmethods, apparatus, systems and articles of manufacture are merelyillustrative and should not be considered as limiting. For example, itis contemplated that any or all of these firmware, hardware, and/orsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware, or in any combinationof hardware, software, and/or firmware. Accordingly, while the followingdescribes example methods, apparatus, systems, and/or articles ofmanufacture, the examples provided are not the only way(s) to implementsuch methods, apparatus, systems, and/or articles of manufacture.

Certain examples provide mobile applications for blood centers thatinclude donor, administration, operations, and/or service applications.Certain examples converge information into one application that helpsprovide improved record keeping, better donor experience, reduction ofwaste, and/or enhanced ease of use for the user, for example. Inaddition, flow of communication can be improved throughout the supplychain. Furthermore, certain examples help provide for automation ofmanual tasks which would eliminate or reduce potential user errors.

In certain examples, an application can provide training, feedback,monitor, and status information on a collection process. For example, anapplication on a mobile or handheld computing device (e.g., an AppleiPad™, iPhone™, and/or other tablet computer or smartphone) can helpfacilitate user training with respect to one or more blood collectionand/or processing procedures. For example, use of equipment and suppliesmay be facilitated.

In certain examples, a customer may purchase an application and/ordownload the application to a device. Materials may be provided toexplain the application, provide directions for downloading/installingthe application onto a phone, and/or explain how to use the application.In some examples, an application can give visual assistance in operatinga device such as Fenwal's Alyx™ or Amicus™ collection instrument. Insome examples, the application may provide a mobile version of theoperator's manual for the Alyx™ system and/or the Amicus™ separator.

In some examples, an application may make provider websitesmobile-friendly. For example, Microsoft SharePoint™ supports mobileviews and can be leveraged to provide a mobile-friendly provider (e.g.,Fenwal) website.

In some examples, an application for use with a mobile device isintegrated with a provider (e.g., Fenwal) data management system. Insome examples, the application enables the device to be made 21 CFR part11 compliant. In some examples, the application can be used across avariety of blood products.

Mobile Applications

In certain examples, an application can provide training, feedback,monitor, and status information on a collection process. For example, anapplication on a mobile or handheld computing device (e.g., an AppleiPad™, iPhone™, and/or other tablet computer or smartphone) can helpfacilitate user training with respect to one or more blood collectionand/or processing procedures. For example, use of equipment and suppliesmay be facilitated.

In certain examples, a customer may purchase an application and/ordownload the application to a device. Materials may be provided toexplain the application, provide directions for downloading/installingthe application onto a phone, and/or explain how to use the application.In some examples, an application can give visual assistance in operatinga device such as Fenwal's Alyx™ or Amicus™ collection instrument. Insome examples, the application may provide a mobile version of theoperator's manual for the Alyx™ system and/or the Amicus™ separator.

In some examples, an application may make provider websitesmobile-friendly. For example, Microsoft SharePoint™ supports mobileviews and can be leveraged to provide a mobile-friendly provider (e.g.,Fenwal) website.

In some examples, an application for use with a mobile device isintegrated with a provider (e.g., Fenwal) data management system. Insome examples, the application enables the device to be made 21 CFR part11 compliant. In some examples, the application can be used across avariety of blood products.

FIGS. 1-5 show example interfaces for current and/or potential blooddonors (e.g., with respect to Donors A-E). For a donor, an exampleapplication can track donation history. The application can notify adonor when he/she is able/available (e.g., based on donation guidelineeligibility and/or schedule availability) to donate. An exampleapplication can allow for the donor to enter donation goals, e.g., 30liters, and provide a thermometer type of graph on the donor's progressto the goal. The goal graph can be broken down into smaller goals, forexample. At each smaller goal, a pop up and/or other dialog box and/orindicator can be provided to explain how many people the donor helped(e.g., at five liters (5 L) a donor helps ten people that underwentemergency surgery, etc.). In some examples, donors can be shownincentives that can be received after a set amount of donations (e.g.,30 donations=$25 gas card, etc.). The application can also enabletracking of different blood components (e.g., red blood cells (RBC),plasma, platelets). For each component goal it would have theappropriate people helped (e.g. a donor's five units of plateletsdonated were used to help three chemotherapy patients. The applicationcan also compare the donor to an average donor/donors (e.g., frequencyof collections, units collected, etc.).

The application can enable a donor to post his/her goals and collectionsto a webpage, such as a Facebook™ page or Twitter™ account, etc. Awebpage can also be provided to explain the donation process, thetechnology, why to donate, the benefits of a double red blood cell(2RBC) procedure versus whole blood collection, etc.

In certain examples, the application can provide locations for upcomingdonations and/or can link with online (e.g., Google™) maps and/ordirections. The application can also prioritize the donation locationsthat feature a particular (e.g., Fenwal™) technology and/or need acertain blood component, etc. In certain examples, based on tracking ofa donor's location, a nearby donation facility can compare a currentinventory (and associated need) with the tracked donor's information(e.g., blood type, eligibility, etc.)

In certain examples, announcements and/or requests can be pushed to adonor's mobile device by the donation facility. For example, informationcan be pushed to one or more donors based on donor specificcharacteristics, a need for a particular blood component and/or arelationship of the donor to the blood collection facility (e.g., donorblood type, donor characteristics, proximity, membership, registration,prior donation at the facility, etc.).

In certain examples, donor information can be pushed to a donationcenter and used information to send relevant information to the donor.For example, the donor's goal/progress/location information is pushed toa donation center computer, and then the donation center can send thedonor reminders to donate. Alternatively or in addition, if there is aneed for the donor's specific blood type, the donation center can send auser a specific message related to the donor's goals (e.g., pleasedonate and you will reach your personal goal of x). News or humaninterest stories can also be sent to particular donors based on donorcharacteristics, need for blood, and/or a relationship to the bloodcollection facility, for example.

In certain examples, an application can provide feedback on thecollection process. The application can diagram the procedure (e.g., armto centrifuge to final product storage in real time). In certainexamples, another part of the application can monitor flow rates of thevein with a game style interface with the donor trying to keep the flowrate in an optimal window. For example, the donor can squeeze a mobilecomputing device at specific intervals to control and/or optimize flowrate. The mobile computing device can indicate how well the donor iscontrolling the flow rate during the procedure based on an internalaccelerometer, touch screen, and/or other suitable mechanism. This canalso link up with other donors and they can “compete” against each other(e.g., akin to the carnival game of filling up a water balloon withwater).

In certain examples, a blood collection/processing machine and/or adonor application communicates with a donor's mobile device (e.g., aphone) based on donor characteristic(s) and/or donor location. Forexample, after a donation, a donor's movement may need to be restrictedfor a certain period of time. If the donor does move, the donor'smovement can be detected via the mobile device and/or other monitor, andthe mobile device can generate and/or relay an alert (e.g., the mobiledevice can vibrate, sound an alarm, notify the blood donation centerand/or blood collection machine, etc.). Thus, compliance with donationrules, guidelines, best practices, etc., can be facilitated via a mobileapplication.

In certain examples, an application enables a center to pushannouncements and upcoming events to donors. The application can providelinks to enable the donor to schedule his or her donation and maps oflocations where he or she can donate, for example. As discussed above,targeted donation requests and/or announcements can be pushed to a donorbased on location, preference, eligibility, etc.

As illustrated, for example, in FIG. 1 , a mobile computing device 100,such as a smart phone or tablet computer, etc., includes a donationapplication 101 that is selectable by a user via an interface of thedevice 100. The application 101 includes a menu 110 indicating, forexample, a remaining time and date for next donation eligibility. Themenu 110 includes one or more options for user selection including toschedule a donation 111, view goals and progress (toward the goal(s))112, view donation history 113, view year to date statistics 114, seeavailable technology 115, and settings 116, for example.

Selecting to schedule a donation 111, for example, provides a donationscheduling interface 120. Via the donation scheduling interface 120, auser can view nearby blood center(s) 121, view upcoming events at bloodcenters in the area 122, schedule a donation at a default blood center123, etc. The schedule donation option 111, 120 allows a user toschedule a donation based either on a default blood center 123 or via asearch for blood centers in the area 121. The application can interfacewith a map service, such as Google Maps, to display nearby facilitiesand provide driving directions and/or operating hours for thefacilities. In addition to scheduling appointments, the application canalso display upcoming event(s) for blood center(s) in the vicinity.

For example, by selecting to view nearby blood centers 121 from theschedule donation menu 120, a blood center map view 130 is displayed.The map view 130 shown in the example of FIG. 1 provides a graphical map131 and an option to view available blood center(s) as a list 132. Forexample, a user can select a blood center on the map 131 and will thenbe prompted to get directions or schedule an appointment.

In a blood center list view 140, shown for example in FIG. 1 , a listingof available blood centers 141, 142, 143 within a certain area areprovided for user selection. Via the interface 140, a user can getdirections 144 or schedule a donation 145 for a selected blood center141, 142, 143. By selecting to schedule a donation 145, a view ofavailable times 150 is provided, which tells the user his or her nexteligibility to donate and provides one or more available times 41, 142,143 for a selected blood center. The user can select on any of theavailable times 151, 152, 153 or view a full calendar 154 showing theavailable times. By selecting a time 151, 152, 153, a confirmationscreen 160 is provided to summarize the scheduled donation and provideinstructions for the donation, for example. The user can then confirmthe donation appointment 161. Selection of confirm the donationappointment 161 reserves the time at the selected blood center and sendsan email to the user to confirm. The user can also receive anappointment to put in his or her electronic calendar, for example.

Additionally, by selecting to view upcoming events at blood centers inthe area 122, a listing of upcoming events 170 can be provided. Incertain examples, a user can select an event 171, 172, 173 to viewadditional information and/or register for an event.

As illustrated, for example, in FIG. 2 , selection of the goals andprogress 112 option in the main menu 110 provides a donation goalsscreen 220. The donation goals 220 provide one or more blood componentdonation goals, such as platelets (e.g., 20 products) 221, red bloodcells (e.g., 5 units) 222, plasma (e.g., 10 liters) 223, etc. The usercan edit goals 224 and/or view progress 225. The edit and/or progressmay be with respect to all goals, to one or more selected goals, etc.For example, by selecting the plasma goal 223 and selecting viewprogress 225, a plasma progress screen 230 is displayed.

The example plasma progress screen 230 provides a visual representation231 of the user's current progress toward the plasma goal. Additionally,the progress view 230 provides an indication 232 of an amount of plasmaremaining to reach the plasma goal. In the example of FIG. 2 , if amilestone has been reached along the way to the goal, an indicator andoption for additional information 233 may be provided. By selecting theoption 233, a milestone screen 240 is displayed.

The milestone view 240 provides information 241 regarding use of donatedblood product(s), as well as an incentive 242 provided to the user. Forexample, the user may be told 241 that his or her 4 liters of plasmadonated have helped 8 individuals undergoing emergency surgery. Anincentive 242 can also be provided, such as a $25 gift card from theblood center, for example. By selecting an incentive 242, a user canredeem the incentive. The redemption becomes active once the donor hasachieved the milestone, for example. Multiple milestones can be listedand activated once achieved, for example. In certain examples,incentives and milestones can be compared between donors, pitting donorsin a friendly competition or game to participate in blood donationand/or spread word of a need for donation of a blood component.

Thus, the goals and progress option 112 allows the user to set personalgoals for different blood components. The goals are editable by theuser. Progress can be tracked alphanumerically and/or graphically, suchas using one or more thermometers tracking a rise toward the goal. Theprogress can show progress to an overall goal along with progress to oneor more incremental goals. At various milestones (e.g., incrementalgoals), incentives can be awarded along with information regarding howthe blood component(s) may have been used to help those in need (e.g.,patients). In certain examples, collection goals can be integrated withsocial networking sites, such as Facebook™, Twitter™, etc.

FIG. 3 depicts an example in which the donation history option 113 isselected from the main menu 110 of a blood donor application 101 on amobile or other computing device 100. A history view 320 provides anindication of last donation 321, next donation eligibility 322, etc.,along with a complete donation history 323, for example. Selecting thecomplete history option 323 provides an extended history view 330. Theextended view 330 includes a last donation 331, as well as a number ofprior donations 332, 333. If prior donations exceed viewable space,options to navigate a previous page 334 or a next page 335 may beprovided, for example.

Selection of the donation history option 113 allows the user to see hisor her last donation along with real time (or substantially real timegiven some system access, processing, and/or transmission delay)information regarding a remaining deferral period. The complete donationoption 330 allows the user to view information such as where, when,what, how much, and on what device the user donated in the past. Thedonation history can also be integrated with social networking such asFacebook™, Twitter™, etc.

FIG. 4 shows an example product selection interface 420 to access yearto date donation statistics based on selection of that option 113 viathe main menu 110. The product selection view 420 provides a selectablelist of blood products, such as platelets 421, plasma 422, red bloodcells 423, and whole blood 424. Selecting a product, such as plasma 422,provides a view of year-to-date donation statistics 430 for the selectedblood component. As illustrated in the example plasma year-to-datedonation statistics screen 430 provides an indication of the user'sdonations 431 (e.g., 4 liters of plasma donated over 8 donations in theyear-to-date). An indication of potential plasma yet to be donated forthe year 432 (e.g., the user can potentially donate up to 14 liters overthe course of 28 donations) can also be displayed via the view 430.Additionally, one or more averages 433,434 can be provided. For example,a worldwide average 433 of 2 liters of plasma over 4 donations can beprovided, as well as a regional (e.g., country or state-based) average343 of 2.5 liters over 5 donations in the US. The statistics view 430can also provide information regarding a donation leader, such as aglobal leader 435 (e.g., 10 liters over 20 donations).

Thus, the user selects the product/donation type for which he or she isinterested in viewing statistics. The screen 430 provides informationrelated to the amount the user has donated 431, the amount the user hasdonated 432, how much additional product the user could potentiallydonation 433, the average year-to-date donation for world 433 and region434, and the top donor in that category 435, for example.

FIG. 5 illustrates an example selection of the technology option 115from the menu 110. A technologies interface 520 includes a set ofavailable devices or technologies available for blood productcollection. Using the technologies screen 520, the user can accessinformation about the different devices. The technologies view 520 canbe used as a tool to promote automation and to educate donors regardingthe different technologies to encourage donations and to ease fear orconfusion about different procedure types.

For example, the technologies 520 can include one or more availabletechnologies, such as Amicus™ separator 521, Alyx™ system 522,Autopheresis-C™ system 523, and Whole Blood 524, allowing the user toselect a technology 521, 522, 523, 524 to view additional informationabout the selected technology. For example, selecting the Amicus™ 521separator provides a detail view 530 including a picture 531 of thedevice and additional information 532 about the device, how itfunctions, what it collects, how the collected component(s) are used,etc.

FIGS. 6-8 show example interfaces for blood collection device operators(e.g., with respect to Operators A-C). For an operator, an exampleapplication can provide instrument troubleshooting. For example, theoperator can enter an alarm code or take a picture of the alarm screenor kit configuration. The application can present possible solutions;provide video(s) to resolve issue(s) if needed/desired/configured; usepicture recognition and help access kit setup issues and provideresolutions; link to a hotline; etc.

In certain examples, the application can provide blood productsavailable to be collected based on donor characteristics. Theapplication can communicate how long the collection would take and thenumber of people helped based on the collection, for example. Theapplication can allow for the transfer of procedure information and logfiles from an instrument using a communication protocol/medium such asWi-Fi™, Bluetooth™, etc. In certain examples, the application cantrigger/push instrument alarms or procedure information to an operator(e.g., receive a text message when an alarm occurs and provide links totroubleshooting if needed/desired/configured). The application canprovide a real time scorecard (e.g., a goal was to collect 15 units withan average turnaround time of 55 minutes). The application can keeptrack of progress and report it back to an Administrator, for example.An operator can also see a “scoreboard” on how the operators/teams aredoing, e.g. team competitions. The application can enable the operatorto photograph a label on a product bag and check to help ensure that thebag and donor are correct and that the correct blood type was labeled.

As shown, for example, in FIG. 6 , a computing device 600, such as asmartphone or other computer, can provide an operator application 601.The application 601 can include an alarm troubleshooting interface 610to assist a device operator in troubleshooting an alarm or errortriggered at a blood collection device, for example. The alarmtroubleshooter 610 can provide the operator with an option to enter analarm code 611, such as via a keypad 620. The alarm troubleshooter 610can also provide the operator with an option to capture an alarm codewith number recognition 612, such as via a capture screen 630. Thecapture screen 630 shown in the example of FIG. 6 allows a user tocapture, such as using a phone and/or other camera device, an alarm codeshown on a collection device 631. Via the capture interface 630, theuser can capture 632, save 633, and/or delete 634 a captured image withcode 631.

Following input of an alarm code, either through manual entry or photocapture, an alarm troubleshooting guide 640 is displayed. Thetroubleshooting guide 640 provides information 641 including an alarmdefinition for the alarm code along with materials to help the userresolve the alarm. For example, text and/or images to assist theoperator in resolving the device alarm can be provided via the interface640. The operator can use the interface 640 to flip between a series ofpictures/images along with supporting resolution text for each pictureto resolve the alarm, for example. A help desk option 642 can beprovided to assist the operator in resolving the alarm, for example.

Selecting the help desk option 642 brings the operator to a help deskscreen 650. The help desk screen 650 provides the user with anopportunity to attach a photograph 651 of an instrument and/ordisposable set up at issue. The user can also provide information via atext field 652 regarding the problem. A listing of photos and/or filesattached 653 can be provided for user confirmation, and the user cansubmit 654 the information to the help desk. Additionally, an option canbe provided for the user to call the help desk 655.

FIG. 7 depicts an example product availability calculator 701 availablevia a mobile and/or other computing device 700. The calculator 701provides a view 710 of devices being used at a facility, such as anAlyx™ system 711, an Amicus™ separator 712, and an Autopheresis-C™system 713. Selecting any of these devices 711, 712, 713 launches adonor information screen 720. The donor information view 720 includes aplurality of values, such as height 721, weight 722, hematocrit 723, sex724, platelet precount 725, etc., for the donor.

Donor values 721-725 can be color-coded, for example, for easyidentification of their status. For example, green indicates that aparameter value has been entered. Yellow indicates that a parametervalue has not been entered but is required, for example. Blue indicatesthat a parameter value has not been entered but is optional, forexample. A value 721-725 can be selected to display a keypad 730, forexample, to enter the parameter value. In certain examples, the keypad730 can only show allowable values and/or other options for a givenparameter 721-725. Additionally, an option 726 can be provided toconfigure one or more inputs, units, etc., associated with the donorvalues 721-725.

Selecting a next option 727 provides a list of allowable blood products740 based on the donor parameter values 721-725. For example, based onentered and/or retrieved donor parameter values 721-725, a red bloodcell product can be made available 741, along with one or more availableyields 742. One or more products can be made automatically andconfigured 743 based on a selected instrument, for example.

Selecting next 744 presents a targeted product summary 750 including oneor more blood products 751 and associated amounts, for example. Donorinformation 752 can again be accessed, for example. An instrument can beprogrammed 753 based on the donor and product information, for example.

FIG. 8 illustrates an example donor type configuration interface 800.The screen 800 includes a plurality of donor parameters, such as height801, weight 802, hematocrit 803, donor blood type 804, platelet precount805, etc. Values 801-805 can be entered using a keypad 810, for example.A configuration option 806 for inputs, units, etc., can be provided. Auser can also access a product/donor matching interface 820. Using thematching interface 820, an operator can photograph a label on a productbag, for example, and the label is checked to help ensure that the bagand donor are correct and that the correct blood type was labeled.

As shown in the donor/product matching screen 820, a picture of a redblood cell bag label 821 is provided along with a donor blood type 822.When ABO match 823 is selected, the system either accepts the match orindicates that an ABO match has not been found (e.g., via flash, sound,message, etc.). The interface 820 allows an image to be captured 824,saved 825, deleted 826, etc.

FIGS. 9-11 illustrate example interfaces for blood center administrators(e.g., with respect to Administrators A-C). For an administrator, anexample application can provide a booking/scheduling tool; blood typesneeded, demand, available timing for instruments, etc. The applicationcan push announcements from the administrator to donors and/or operatorsregarding upcoming events and/or desired for donation/collection. Theapplication can be used to submit complaints or issues experienced usingsimple forms with an ability to submit photos of issues.

FIG. 9 depicts an example mobile device 900 including an administrationapplication 901 for blood center and/or collection deviceadministrators. The application 901 provides a toolbox 910 including adashboard 911, goals 912, inventory 913, etc. Selecting the dashboard911, for example, provides a dashboard view 920, including one orinstruments in use, such as an Alyx™ system 921, Amicus™ separator 922,and Autopheresis-C™ system 923.

Selecting an instrument, such as the Autopheresis-C™ system 923,provides a status view 930 for the selected instrument. The status view930 includes a layout 931 of one or more instruments at a facility, forexample. The screen layout 931 can match a room layout, for example. Oneor more colors and/or other indicators can be used to determineinstrument status (e.g., in-use, available, instrument alarm, etc.).

Selecting a particular instrument from the layout 931 provides moredetailed status information 940 for that device. The device status(e.g., Autopheresis-C™ Plasma #5) provides additional information 941regarding a procedure being executed at the selected device, such astime remaining, elapsed time, operator, etc. Additional informationregarding the procedure can be displayed, such as a product volumecollected graph, etc. Information on one or more active alarms 942 forthe device can also be provided, for example. Information can be sent toFenwal 943, for example.

Instrument interface 950 depicts another example device interface for adevice (e.g., Autopheresis-C™ Plasma #3) that provides a status 951 ofavailable. A user can select the status 951 to reserve and program thedevice via the interface 960. Via the example reservation interface 960,the user can specify a donor identifier 961, donor parameters 962,special settings 963, etc., to provide a program to the instrument 964.

Using the administrator toolbox 910, the user can also selects goals 912to access a goals screen 1020, as illustrated in the example of FIG. 10. The goals 1020 provide user options to update goals 1021 and/or viewcurrent goals status 1022, for example. To update goals 1021, the useris provided with a goal entry interface 1030, which lists goals for oneor more blood products, such as red blood cells 1031, platelets 1032,plasma 1033, etc. A user can select a blood product 1031-1033, such asplatelets 1032, and then enter a blood type 1040, such aspositive/negative 1041, type O 1042, type A, 1043, type B 1044, and/ortype AB 1045, each of which can be associated with a collection/donationgoal. Each of the blood type goals for the product can be edited using akeypad 1050, for example. The user can also view current goals status1070, including one or more products, such as red blood cells 1071,platelets 1072, plasma 1073, etc. Goals can be for a day, week, month,year, etc. Goals can be updated automatically from a data managementsystem, such as the instrument, for example. A blood component 1071-1073can be selected to provide current blood type goals 1070 for theselected product.

Using the administrator toolbox 910, the user can also selects inventory913 to access an inventory interface 1120, as illustrated in the exampleof FIG. 11 . The inventory view 1120 provides a view of instruments byproduct type 1121, part number 1122, etc., and/or track orders 1123.Selecting product type 1121, for example, provides a product typelisting 1130, including, for example, Alyx™ system 1131, AMICUS™separator 1132, Autopheresis-C™ system 1133, etc. Selecting a producttype, such as Alyx™ system 1131, provides a detail view 1140 for theselected product, including one or more part numbers 1141, 1142 alongwith a number of kits remaining. A note, alert or reminder 1143 can beprovided, such as a note reminding the administrator that 50 kits for apart number will expire in 10 days. The user can select a part number1141, 1142 to view additional information regarding that part 1150. Fromthe part view 1150, the user can review a history 1151, orderinformation 1152, etc. for the part.

Certain examples provide a dashboard application that can provide statusof instrument(s) on the floor, alarms, donation status, time remaining,instrument turns, idle time, etc. A dashboard can also provide for theend of the day summaries. The dashboard can provide an ability toforward this information to a provider (e.g., Fenwal) if servicing isneeded/desired/due.

An application can push donor information to an instrument topre-program the instrument with donor preferences (e.g., smaller veinsso the application sets the instrument at a slower flow ratio). Theapplication can be configurable by a blood center and can enable bloodcenters to compete in a bracket-type contest for donations. Theapplication can push thank you notes and availability of next donationsto donors. The application can push reminders and/or alerts regardingdonation guidelines, best practices, etc., such as to alert an operatoror donor that the donor has left a donation center too soon afterdonating, for example.

Example applications provide an inventory management tool including kitsused, kits remaining, etc., and can push novices for expiry of upcomingkits; link or push notification for ordering new inventory; allow forthe photographing of a barcode to recall inventory data, etc.

For a provider, certain examples can help provide operator application,service troubleshooting, issue resolution help and/or enable proactivemaintenance. For sales, an application can help track customerperformance and usage rates, sales trends, complaints, etc. Anapplication can be provided for new sales training, new publications,market data trends, events, etc.

Additional Mobile Device (e.g., Phone) Applications

In certain examples, one or more applications for a mobile and/or smartphone (e.g., an iPhone™ or BlackBerry™) are provided. When downloaded,this application causes a small icon in the shape of a blood drop orsome other symbol or graphical representation typically associated withdonating blood to be displayed on the main screen of the phone. Thisicon can be located in a corner of the main screen so as not tointerfere with another main screen feature, for example. However, theicon may be displayed at any location on the screen. Within the icon,text can be displayed to show the user's distance from the nearest bloodcollection center (as shown in, for example, FIG. 12 ). Alternatively orin addition, alphanumeric data and/or another visual can be providedwithin and/or superimposed upon the graphical representation (e.g., theblood drop) to convey information, such as donation statistics,countdown to donor eligibility, etc., via the icon without the useropening/executing the application, for example. Further informationand/or functionality can then be provided through execution of theapplication associated with the graphical representation on the mobiledevice.

FIG. 12 illustrates an example mobile device 1200 including a donorapplication 1210 showing a user's distance (e.g., three miles) from ablood donation center. The example application 1210 is represented by ablood drop graphic in FIG. 12 .

When the blood drop icon is touched, an information screen may bedisplayed, such as the example screen of FIG. 13 . In some examples, theinformation may be associated with a fixed collection center that isclosest to the user. When displaying this information screen, the phonecan vibrate and/or emit a sound corresponding to that of a heartbeat fora short amount of time. This screen can include the nearest bloodcollection center's: a.) corporate logo or symbol 1310, b.) address1320, c.) building or profile picture 1330, d.) phone number 1340, e.) asnippet of a Google™ (or other equivalent) map showing the bloodcollection center's location on the map 1350, f.) an icon in the shapeof a blood bag showing the nearest blood collection center's currentmonthly collection total, as well as its target monthly collection goal1360, g.) a small provider (e.g., Fenwal) logo 1370, and/or h.) a backbutton 1380, for example.

A more detailed description of some of the items on the informationscreen is provided. For example, when the phone number (d) is touched,the phone can automatically call the nearest blood collection center'srecruitment or scheduling department. In this manner, the phone user isenabled to schedule an appointment to donate blood if he or she sochooses. When the phone conversation is ended, the user can be broughtback to the phone's main screen.

The blood bag icon (f) displays a nearest blood collection center'scurrent monthly collection total as well as its target monthlycollection goal, for example. This data can be made available to theapplication using the phone's built in Internet and/or other networkcapabilities to access a registration website. As illustrated, forexample, in FIG. 14 , a blood bag 1400 would “fill up” as the currentmonthly collection total approaches the target monthly collection goal.A goal 1410 can be provided with respect to the bag or other graphic1400, such as a goal of 5000 units by Jan. 31, 2010. A current status1420 can indicate, for example, that 2200 units have been collected asof Nov. 10, 2010. As the month progresses, the graphic 1400 can indicateprogress 1430 toward the goal 1410 (e.g., 4750 units as of Jan. 21,2010).

In this way, the user quickly determines how significant the nearestblood collection center's current need for blood may be. In someexamples, the date that the data was last updated may also be displayed.In some examples, the blood bag icon may be an optional feature. Forexample, when a blood bank center registers, it may select not todisplay the blood bag icon and, thus, the center would then not have toupdate the data regarding its current monthly collection total and/orthe target monthly collection goal. If a center decides to include theblood bag icon, data may be input by the center to keep the data up todate. For example, the registered blood collection center may update thecurrent monthly collection total and/or the target monthly collectiongoal on a daily basis. In some examples, the data may be entered usingthe same website as used to register the collection center. In someexamples, the center may register on-line. In some examples, whenregistering, the center may upload and/or provide their address,corporate icon and/or a picture of the building where it is located.

In some examples, the blood drop icon on the main screen provides theuser with an unobtrusive but constant reminder of the need to donateblood. Rather than utilizing potentially annoying phone calls asking thedonor to come back again and donate, blood centers participatingapplication project and/or utilizing the examples descried herein willnow have a means of continuously reaching out to their donor base viaregistry of their blood collection centers on the registration website.The application enables 24 hours a day, 7 days a week passiverecruitment that is not disturbing to the donor.

In some examples, once an application is installed, it continuously, butin the background, accesses the registration website using a phone's(e.g., an iPhone™ or other smart phone) built in Internet and/or othernetwork capabilities and calculates the user's distance from each bloodcollection center in each account by retrieving the street addressesstored in the registration website and then providing these addresses tothe phone's built in global positioning system (GPS) and/or otherlocation function. The GPS function then calculates the user's distancefrom each registered blood collection center and/or may providecorresponding route information upon selection, for example. In someexamples, the application interacts with public-access map tools suchas, for example, MSN™ Maps, Google™ Maps, etc., and then, once received,the application may display the distance that the user is from the bloodcollection center. In some examples, the application enables the user toselect which of the public-access map tools are utilized.

In some examples, after the user's distance from each registered bloodcollection center is determined by a phone's GPS function, theapplication may automatically select the closest blood collection centerand display the distance of the blood collection center from the user(e.g., in miles) within the blood drop icon on the main screen. In someexamples, the user can select one of the blood collection centers theywish to go to and appropriate directions to the selected bloodcollection center may then be retrieved and then displayed.

When the map snippet (e) is touched, it can automatically activate thephone's built in global positioning system (GPS) and/or othergeolocation/terrestrial location function and begin providing the userdirections from his or her current location to the location of thenearest blood collection center, for example. A back button can beincorporated to enable the user to navigate back and forth from the GPStool to the information screen.

In some examples, when the blood drop icon is pressed, the applicationgrabs the data associated with the closest blood collection center,again by accessing the registration website using the a phone's, e.g.,an iPhone™, built in Internet capabilities, and uses this data topopulate the fields that are displayed on the information screen,including, for example, a.) the center's corporate logo or symbol, b.)the center's street address, c.) a building or profile picture of thecenter, and d.) the center's phone number, and/or e.) a snippet of aGoogle (or other equivalent) map showing the center's location on themap, and, if the optional monthly data feature is enabled, f.) thecenter's current monthly collection total and/or the center's targetmonthly collection goal (both of which are used by the blood bag icon((f), as previously described).

In some examples, because, in the background, the application maycontinuously be accessing and analyzing the blood collection center datastored on the registration website, as the user moves about, his or herdistance from the various registered blood collection centers changes.Correspondingly, the data displayed in the blood drop icon on the mainscreen and the data displayed on the information screen may vary and/orchange according to which blood collection center a phone user happensto be closest to at any given time.

In some examples, the blood drop icon on the main screen tells the userhow close he or she is to a blood collection center. Notifying users ofthe nearest blood collection center may notify users of (e.g., enablethe discovery of) blood collection centers of which he or she waspreviously unaware.

In some examples, the information screen may attempt to motivate theuser to donate by providing them with information to locate and contacta blood collection center and/or by communicating to the user thecenter's current need for blood in terms of the center's monthly goals.

In certain examples, when the provider logo (g) is touched, the phone'sbuilt in Internet and/or other network capabilities can be used to bringup a provider's (e.g., Fenwal's) external website.

When the back button (b) is touched, the user can be brought to thephone's main screen, for example. Alternatively and/or in addition,after a certain amount of inactivity while on the information screen,the application can automatically return the user to the main screen.

In certain examples, a user can register the application via aregistration website, accessible over the Internet, an intranet, avirtual private network, etc. The website can be a password protectedpart of or extension to a provider's (e.g., Fenwal's) external website,and the website can be periodically supported by the same group ofpeople who already support the external website. An application mayretrieve data from the registration website and display the data. Incertain examples, an application may involve the creation, and periodicsupport, of the registration website.

The registration website can include a number of blood center accountsand can be used in a variety of ways, including the following examples.

In some examples, participating blood centers may be provided with aunique username and password for access into their specific accountwithin the registration website.

In some examples, when logged into their account on the registrationwebsite, the blood center can register by providing: a.) a streetaddress (possibly including hours of operation), b.) a phone number, andc.) a profile picture for each blood collection center that the bloodcenter wishes to register into the application. The profile picture canbe any image of the blood center's choosing, but it is envisioned thatit might be a picture of the building corresponding to the registeredblood collection center. Also, the blood center can provide an image ofits corporate logo or symbol.

In certain examples, a mobile collection site can be registered as wellby providing a.) a street address, b.) a phone number, and c.) a profilepicture, as well as by toggling a switch on the website that, whentoggled, requires the blood center to also enter a date (e.g., mm/dd/yy)and a time range (e.g., two specific times between 12:00 AM and 12:00PM). In this fashion, the application can factor the registered mobilecollection site into its nearest blood collection center calculation onthe specific day and time provided. In some examples, there may be alimit placed on the length of time (e.g., one day) that the mobile sitemay be displayed and/or be operating for to ensure that mobile sitesthat are no longer operating are not inadvertently displayed.

In some examples, a blood center can choose whether or not to enable theoptional monthly data feature of the application. In the blood center'saccount on the registration website, the feature can be default set to“off,” but, if toggled “on,” it enables the center to also fill in acurrent monthly collection total and a target monthly collection goalfor each of their registered blood collection centers, for example.

In certain examples, the current monthly collection total can be anumber representing the blood collection center's current number ofwhole blood units collected for the month so far. A current monthlycollection total can be provided for each of the blood collectioncenters registered. The participating center may assign a responsibleperson from each of their blood collection centers with the task ofupdating their respective center's current monthly collection total atan appropriate interval of their choosing (such as daily or weekly).Also, when this number is input or updated, the registration website canautomatically update, set, and/or display the date that the currentmonthly collection total was entered or changed.

In certain examples, the target monthly collection goal can be a numberrepresenting the blood collection center's total monthly whole bloodcollection goal in terms of units collected. A target monthly collectiongoal can be provided for each of the blood collection centersregistered. Again, when this number is input or updated, theregistration website can automatically update, set, and/or display thedate for achieving this goal as equal to the last day of the currentcalendar month.

Thus, if the blood center wishes to support the optional monthly datafeature, they can use their username and password to log in to theiraccount on the registration website and update or change their targetmonthly collection goal(s) and current monthly collection total(s) asappropriate. Because access into the accounts on the registrationwebsite is password protected, misuse or misrepresentation of this datais mitigated since each individual account is set up with a uniqueusername and password.

Referring back to the blood bag icon (f), the data displayed alongsidethe icon is retrieved by the application using the phone's built inInternet and/or other network capabilities to access the registrationwebsite and retrieve the target monthly collection goal and the currentmonthly collection target for the nearest blood collection center.

In certain examples, the blood center can disable the optional monthlydata feature at any time by logging into their account on theregistration website and toggling the feature to “off.” If the featureis toggled “off,” when the application attempts to retrieve the targetmonthly collection goal and the current monthly collection target forthe nearest blood collection center, it will recognize that the featureis toggled “off” and will, accordingly, cease displaying the blood bagicon (f) until it recognizes that the feature has been turned “on”again.

Promotional materials may be used to explain the application project andcan provide directions for downloading the application onto a phone, andthey can also explain how to use the application itself. These materialscan be handed out by the blood center to their donors after they donate.In this way, the blood center can use the application as an incentiveand reward program for their donors. For example, these promotionalmaterials can include a one-time use download code, which can be enteredby the donor prior to downloading the application onto a phone.

In some examples, an application can be used in conjunction withpromotional material by blood collection centers to incentivize theirdonors and reward them after donation. For example, the applicationconstantly travels with a phone, and the phone may constantly travelwith the donor (e.g., all day, every day). Ways for blood collectioncenters to reach out to donors after they donate are to: follow up andcall them, email them, or send them postal mail. These approachesinvolve the blood collection center's time and effort. The applicationdescribed herein allows centers to stay connected to the donors and thedonors to stay connected to the blood centers. One-time mobile donorsmay be more likely to switch over to and become regular fixed sitedonors because the application facilitates an ability to look up contactinformation for fixed site locations.

In some examples, only blood centers using a provider's (e.g., Fenwal)products will have accounts on the registration website. Thus, theapplication can indirectly push donors back to just the blood collectioncenters where a particular provider's name (e.g., Fenwal) is listed.Unless the blood center opts to use the optional monthly data feature,the application, in general, doesn't require anything more than aone-time commitment from each stakeholder (e.g., when registering forthe service).

In some examples, each blood center may only have to register theirblood collection centers once. However, it may remain the blood center'sresponsibility to ensure that their blood collection centers' datastored in their account on the registration website stays accurate andup to date.

In some examples, a provider (e.g., Fenwal) may develop, but notnecessarily support, the application and the registration website. Incertain examples, if a blood center volunteers for but, at a later date,opts out of a participating application project entirely, a provider'sinformation technology (IT) group (e.g., Fenwal) may delete theiraccount from the registration website, for example.

In some examples, a provider (Fenwal) may only have to work with a bloodcenter once to set up their account on the registration website.However, in some examples, a provider may periodically replenish thecenter's stock of promotional material. By displaying corporate logosand symbols, the application provides advertising for both the provider(e.g., Fenwal) and for those blood centers that choose to participate inan application project.

In some examples, the donor may only have to install the applicationonce and is not obliged to interact with the application in any otherway after its initial installation.

In some examples, the blood center may further incentivize a donor thatutilizes the application by providing him or her with a code that, whenaccepted by the application, keeps track of his or her number ofdonations. For each donation, the donor receives another code and/orpassword. After a specified number of donations are acquired, the blooddrop icon can update (see, for example, FIG. 15 ). For example, adonor's blood drop icon 1410 can progressively update to a moreimpressive symbol 1520, 1530, 1540 as his or her number of donationsincreases.

In some examples, using data stored on the registration website, theapplication can keep track of a blood collection center's target versusactual collection amounts for each month over a one year window, etc.,and, when the blood bag icon (f) is pressed, the application can displaythis information to the user.

FIG. 16 depicts an example histogram 1600 that can be displayed after auser presses the icon (e.g., the blood bag icon) on the informationscreen. The histogram 1600 can display information to a donor such as,whether or not his or her monthly target has been met. Additionally oralternatively, the information displayed may indicate the amount over orunder the monthly target amount that the donor is. In some examples, thebackground of the histogram may be selected by the user, berepresentative of the seasons (e.g., fall, winter, etc.) and/or includea corporate logo (e.g., Fenwal). Depending on the origination of themobile device (e.g., an iPhone™, BlackBerry™, and/or other smart phone),the display of the histogram may change. In some examples, the histogrammay display past targets for blood collection centers and/or the amountreceived for a particular and/or specified amount of time. For example,as illustrated in FIG. 16 , a month 1610, monthly total 1620, and season1630 can be displayed along a timeline for the donor.

Tracking Donated Blood

Donated blood is to be tracked and triaged. When blood is collected froma remote site, it can be difficult to communicate to the main officewhich unit is being collected at what time and where the unit is locatedat the present time. In many cases it is important for the blood centerbecause some/many units need to be processed within an eight hourwindow, such as for plasma. Currently, this is being decided when theunits are coming in by searching through hand-written notes thatcollection staff recorded at the point of collection. This process iscalled triaging. Until blood process staff go through entire units thatare coming in, they do not know which unit is time-sensitive. Also,tracking during transit can be problematic. One can sometimes call thedriver to ask the location of the van, but the driver does not alwaysknow which unit he is carrying back.

In some examples, using a phone (e.g., an iPhone™ or some other mobiledevice), the operator can record a DIN (donor identification number) andcollection time. In some examples, using a phone or some other mobiledevice, the operator can record additional optional information such asgender, blood (ABO) type if known, weight of the unit, etc. In someexamples, using a phone or some other mobile device, the operator canrecord a “cooler number” that the unit of collected blood is going in.In some examples, using a phone or some other mobile device that isattached to, coupled to, or incorporated with the cooler, the mainoffice can track individual unit(s). In some examples, using a phone orsome other mobile device, the units are tracked as they are coming intoblood center. Thus, the blood center knows which unit(s) is/are timesensitive, for example.

In some examples, using a bar-code reader application, one can recognizethe product code and DIN. In some examples, an example application canautomatically load the information into an e-mail system and/or datasystem and automatically send the e-mail or data to a main computer(s).At that time, additional information can be added as well. For example,a “cooler” can have an identifier as well. The identifier may be abar-code or an assigned number, for example. As the operator puts theunit in the cooler, the operator can open the example application andfind (e.g., scroll down) the unit he or she is working with, and add thecooler information by punching the number or bar-code scanning, forexample. Another e-mail or data may be sent (and/or be combined with theemail with produce code and DIN above), for example. In some examples,the cooler itself has a phone and/or other communication device (e.g.,an iPhone™ and/or other smart phone) attached. Using a tracking program,an operator or user can track the phone/device that is attached to thecooler. Since the main computer knows which unit is placed in whichcooler (e.g., the unit associated with the cooler when placed therein bybar-code scanning), individual units are being tracked, for example. Insome examples, in a receiving dock, operator(s) have a phone withtriaging information being pushed to the phone. The information includeswhich units have to be triaged first, for example. The operator looksfor the cooler and finds the unit and processes the unit accordingly. Insome examples, as the operator selects six units to process, he or sheopens the example application and looks (e.g., scrolls down) for the sixunits and checks out the six units. The main computer knows who has thepossession of those units.

Interactive Teaching Application

FIGS. 17-19 depict example screen shots of a mobile device (e.g., aniPhone™, iPad™, and/or other smart phone or handheld computing device)running an application that increases blood/plasma donor awareness. FIG.20 depicts an example flowchart for the application. For example, theapplication may convey information related to the number of lives savedbased on the amount and/or frequency of the donor's donation(s) (asillustrated in FIG. 17 , for example). In some examples, the applicationmay convey information related to the number of lives saved based on theamount and/or frequency of donations by the donor's friends and/orfamily, sponsored by a provider (e.g., Fenwal) (as shown in FIG. 17 ,for example).

In some examples, an application may provide a convenient tool and/orapplications including maps and/or directions to the nearest donationfacility/facilities (as illustrated in FIG. 18 , for example). In someexamples, the application may provide a convenient tool and/orapplication(s) that includes a personalized donation schedule (e.g., thedate that the donor is next eligible to give a donation, as shown inFIG. 19 , for example) and access to “donation buddies” schedules (e.g.,donation schedules) by encouraging users to share the applications withfriends and/or family members.

In some examples, an application may be a mobile donation stationapplication that provides a common platform for donors and/or thegeneral public to gain an understanding of cumulative lives saved basedon frequency and/or the quantity of blood/plasma donations (as depictedin FIG. 20 , for example).

As shown in the example of FIG. 20 , a user 2010 accesses donationrecords and/or schedule 2020. Using the records/schedule 2020, the user2010 can retrieve one or more donation locations 2040, for example. Theuser 2010 can also access a user group 2050 for information such as anestimate of a number of lives saved 2030 by blood donations, forexample.

By utilizing the applications and the examples described herein, aprovider (e.g., Fenwal) utilizing a phone and/or mobile deviceapplication (e.g., an iPhone™), for example, may gain improvedvisibility. In some example, other institutions, blood banks,affiliates, etc. may be provided with access to a database of users thatare utilizing the application.

In some examples, the application promotes donor awareness of thebenefits of donating blood/plasma, etc.

In some examples, the application may provide a chart that details RBC,plasma, and/or platelet collection levels for the donor's center, theentire state, and/or the country (e.g., detailing collection levelsversus need levels, etc.). In some examples, the chart may provide avisual representation of how their donation affects the overall group ofdonors. Such an approach of visually representing donor center levelsmay increase donor awareness of the need to donate and/or perhaps urgethem to convince others to donate as well.

In some examples, an interactive application teaches donors about blood,the therapeutic uses of the various blood components, and/or how theautomated Fenwal technologies or other provider technologies aredesigned to maximize the collection of platelets (e.g., on an Amicus™separator), plasma (e.g., on an Autopheresis-C™ system) and red cells(e.g., on an Alyx™ system). This application may also include some basicinformation about how the automated devices function. In some examples,the application may describe how they draw the donor blood in, separateit into the various components and return the unnecessary componentsback to the donor. In some examples, the target audience may be theyounger donor population. In some examples, the application may be givento whole blood donors during their donation to educate them about how tobenefit more patients with a single donation when donating usingautomated technology. The application educates the donors, which maymake them come back more often, and promotes a provider's (e.g., Fenwal)automated technologies.

Blood Component Loss Calculation

The examples described may include an application that enables RBC andplasma loss on an instrument such as an Amicus™ system to be calculatedif they cannot re-infuse the donor. For example, the application cancalculate and/or determine the answer by having a person enter if it isa single needle (SN) or double needle (DN) procedure, what the donor'shematocrit is, and/or what cycle volume they were using if it was a SNprocedure.

Blood Collection Screening Application

In some examples, an application enables donor screening for automatedcomponent collections by, for example, providing a brief donorquestionnaire to determine if a donor qualifies for apheresis donationsbased on donor sex, height, weight, blood type, CMV+/−, etc., andidentify any special needs for donor's blood type or specificcomponents, and/or provide a brief video or slideshow explaining theprocedure(s) to the donor. Blood centers can enter daily collectiontargets to customize options.

Blood Donation Tracking, Reminders, Scheduling and/or MedicalInformation

In some examples, the application allows donors to make appointments ata blood center, and/or the application may enable the center(s) toremind the donors of their appointments. In some examples, theapplication enables scheduling systems of different blood centers tointeract to facilitate scheduling of donors.

In some examples, an application enables a donation calendar thatenables regular donors to track their donations and set alarms toschedule appointments when donors are eligible for their next donation.Certain examples provide an option to download donation history fromblood center websites or manually enter data to track blood pressure,cholesterol, etc. Certain examples locate nearby blood centers (e.g.,utilizing GPS) by referencing, for example, a Fenwal database.

In some examples, by providing an application, accessible and/orexecutable by phone (e.g., a smart phone such as an iPhone™), a bloodcenter can access mobile society communication channel(s). Through suchan application, a blood center can maintain near constant connectionwith donors to help build donor loyalty and potentially improve donorfrequency. The application can connect with a blood center's existingsoftware systems.

The application can alert donors when they are approaching donationeligibility date and locate daily mobile blood drives near their currentlocation, for example. Using the application, a donor can schedule hisor her next donation using a “make appointment” function, or place adirect call to the blood center, if the donor prefers. Using theapplication, a blood center can connect with donors frequently but notin a manner that will be perceived as intrusive. Potentially, donorfrequency can increase. In some examples, incentives can be providedthrough participation to help increase donation frequency. Donor accessand scheduling can be tracked by call center staff, application reports,etc. Donor activity can be tracked via spreadsheet, one or more datafields in customer relationship management (CRM) software, etc.

In some examples, donor appointments can be tied to electronic calendars(e.g., Outlook™, Google™, etc.) via the phone application.

In some examples, an example application may be provided for donors touse to keep track of when, where, and/or what they last donated (plasma,red blood cells, etc.). This application may have reminders built intothe application and enable donors to set reminders as they like.

In some examples, an application may be integrated with a phone's (e.g.,an iPhone™) built-in calendar or other calendars so users can keep theirdonation appointments with their other calendar data. In some examples,general donation information such as why someone should donate, someinformation about blood types, etc. may be provided by the application.

In some examples, an application reminds donors that it is time todonate blood, plasma, etc. again. In some examples, the applicationdetermines and/or checks the next time that the donor can donate. Insome examples, an application records, stores and/or accessesinformation relating to previous donations and conveys this informationto the donor.

In some examples, an application may serve as a scheduling assistant.The application can sort the contacts list by key data such as deferraldates or recommended procedure type, for example.

In some examples, an application may use a phone's location services tohelp and/or enable a donor find a local donation center.

In some examples, a donor's particular information can be segmented fromother donor information. In some examples, donor information for oneblood center can be segmented from donor information for other bloodcenters. Data requests, such as a time taken for a donor to return togive blood after he or she is again eligible (e.g., a number of daysafter becoming eligible), donor frequency data by age segment, and/orother data can be determined and retrieved via the application.

In some examples, application icon(s) can be customized based on bloodcenter, donor, and/or other characteristic. A data countdown until donorappointment and/or donor eligibility can be visible via the icon. Donorhealth information and/or other information for the donor can beprovided by the application via icon(s), graphics, text, etc.

In some examples, the application can enable blood centers to conductsegmented pushes to donors that have particular blood type(s).

Mobile Operator Application

In some examples, an application can give visual assistance in operatingan Alyx™ system or an Amicus™ separator. In some example, theapplication may provide a mobile version of the operator's manual for anAlyx™ system or an Amicus™ separator.

In some examples, an application may make provider websitesmobile-friendly. For example, Microsoft SharePoint™ supports mobileviews and can be leveraged to provide a mobile-friendly provider (e.g.,Fenwal) website.

FIG. 21 depicts an example mobile device 2100 including an interfacelisting one or more blood collection/processing instruments 2101, 2102,2103, 2104, 2105 under control of the operator. A device identifier 2110and status 2120 is provided for each instrument 2101-2105. A control2130 can be provided to stop operation of the instrument 2101-2105, forexample. If an alarm has been triggered at an instrument 2101-2105, anindication of the alarm 2140 can be provided as well as an option foradditional alarm information 2150.

Thus, using the example mobile interface of FIG. 21 , system status forall collection systems in a network can be provided to a mobile device2100, such as an iPhone™, iPad™, BlackBerry™, and the like. The statuscan include an instrument number, status, etc., and can provide quickaccess to one or more features such as a stop feature, an alarm feature,etc. The mobile device 2100 can be used as a mobile monitor rather thantying an operator to a stationary desktop or computer system.

In certain examples, the mobile device 2100 can provide a practice forumfor training new operators regarding configuration, use, and/ortroubleshooting of blood collection instrument(s). For example,step-by-step photos, diagrams, and instructions can be shown for properkit loading for one or more devices can be provided. Access to on-lineoperator's manuals, error codes, and/or product information can beprovided via keyword search through the mobile device 2100. In certainexamples, complaints can be submitted via the mobile device interface2100. In certain examples, troubleshooting of instrument operation canbe facilitated using the mobile device 2100.

Reporting Application

In some examples, an application enables a blood center and/or bloodcenter personnel to report an issue (e.g., problem, complaint, etc.) toa provider (e.g., Fenwal).

Certain examples provide complaint reporting. Rather than a paperreport, an operator who experienced an issue first-hand can submit areport and improve a likelihood of including important detail. Theoperator can register the complaint first hand and incorporate productbar code scans and photos that may be important to a complaintinvestigation. Pre-population of information can streamline thecomplaint reporting process, and automatically submitting the report toa vendor via the mobile device 2100 can help save the trouble and timeof faxing the document. Automatic assignment of a complaint numberprovides improved ability to track the complaint through to resolution.

In certain examples, an instrument trouble shooting decision tree canimprove a speed with which an operator is able to resolve an issuerather than potentially delay to make a phone call and find anappropriate person with whom to speak. Also, submitting a servicerequest can be more easily facilitated via the mobile device 2100.

In certain examples, a camera associated with the mobile device 2100 canbe used to scan a product barcode as well as record and submit photo(s)of a complaint issue with the product to facilitate complaintdescription and filing. The camera can be used to record and submitinstrument screen photo(s) with associated error code(s). Barcodescanning of the product retrieves a correct product complaint form thathas been pre-populated with product information. The mobile interfacecan be used to additionally pre-populate the complaint form with centerinformation, date, time, complaint reference number, etc. The mobiledevice 2100 can be used to submit the complaint directly to theinstrument vendor with an option to copy the blood center's e-mail forlocal tracking, for example.

An additional feature can be an instrument trouble shooting decisiontree similar to the practice currently used orally via instrument vendorcustomer service. The decision tree can help the operator 1) resolve theissue or 2) submit a service request either by a) embedded form or b)leading the user to call customer service directly from the mobileapplication.

Cost Analysis Application

In some examples, an application compares how much a donor can make bydonating certain blood components over a certain period of time. Forexample, a donor may make more money donating plasma versus donatingwhole blood. For example, a donor may make more money donating a certainamount of whole blood and a certain amount of plasma. In some examples,the donor can determine if he or she can make more money over six monthsby donating plasma or platelets.

In some examples, rather than being paid for a donation, a donor can beoffered different incentives (e.g., coupons, discounts, recognition,and/or other prize) to continue regular donations over time. Donationsuntil a next incentive can be tracked and displayed to the donor, forexample.

Example Application Having a Game Style Interface

In some examples, an application is a video game that enables donors toadvance to different levels based on the amount of blood donated. Forexample, the application may be a video game where a character (e.g.,Fenny the red blood cell) has to jump from level to level until reachinga new donor and saving his/her life.

Application Used in Connection with Blood Donation

In some examples, an application is provided that a phlebotomist coulduse as a humorous tool to help break the ice with a new donor. In someexamples, the application may be a vein finder set up much like a studfinder and would beep when paced over a supposedly large vein in thedonor's arm.

Blood Processing Application and/or Blood Donation Application

In some examples, an application can display and/or provide informationregarding units of platelets, milliliters of plasma given, one or twounits of RBC, etc. In some examples, an application may display and/orprovide information regarding which arm of a donor was used (e.g., drawand return). For example, the application can display which donor armwas used the last time the donor donated and/or a number of times aparticular arm has been used to donate.

In some examples, an application can display and/or provide informationregarding a next eligible donation date based on an amount of platelets,plasma and/or red blood cells donated. In some examples, an applicationcan display and/or provide information regarding using special features,registering to a provider server (e.g., a Fenwal server) when donated ona provider's instrument (e.g., Amicus™ or ALYX™) for a reward program,such as iTunes™ music by accumulating points.

In some examples, an application includes three main sections; however,any other number of or different sections may be used instead. Thesections can include a personal information section including lastdonation information, eligible date information, current donationinformation including any medical information that can be obtained froma donation site such as blood pressure, pulse, etc., for example. Adonation type (such as whole blood (WB), platelets (Plt), plasma,two-RBC, etc.) can also be provided.

A second section can feature a location at which the donation ishappening (e.g., this week), particularly via mobile collection.Collection sites can be listed and, when selected, a site will bedisplayed including information regarding the blood drive, for example.A link to an electronic map, such as a Google™ map, can be leveraged toshow the route from current position which is available through a globalpositions system (GPS) and/or other positioning system, for example.

A third section can include a registration page for a provider (e.g.,Fenwal) web site. Every time one donates on a Fenwal device, forexample, one can register at the Fenwal site or other affiliatedprovider. Registration can be done at the donation site, and theregistration can record the GPS information of the locationauthenticating the donation. A user can also provide a “key” through theblood collection agency for authentication by way of the application.

Data Management System and/or Catalog Application

In some examples, an application enables the catalog of products (e.g.,Fenwal products) by selecting the product family and code number and theapplication will provide a complete product description such as quantityof bags in the set, type of sampling system, filter type (ifapplicable), solution types and volumes, etc.; providing an electronicform to order products from customer service; and/or providing adatabase to track inventory levels by code/lot number/expiration date asproducts are received and shipped out to other centers or on mobiledrives.

Product Surveillance System

In some examples, an application enables product surveillance bysnapping a picture of product defects and enabling a questionnaire(s) tobe filled out; enabling complaints to be sent electronically to productsurveillance; and/or receiving instructions on how to return the productfor complaint investigation.

Mobile Process Flows

FIGS. 22-24 provide flow diagrams for methods for donors, operators, andadministrators to review and manage blood collection and associatedinstrument information. FIGS. 22-24 depict example flow diagramsrepresentative of processes that may be implemented using, for example,computer readable instructions that may be used during blood collectionoperator training. The example processes of FIGS. 22-24 may be performedusing a processor, a controller and/or any other suitable processingdevice. For example, the example processes of FIGS. 22-24 may beimplemented using coded instructions (e.g., computer readableinstructions) stored on a tangible computer readable medium such as aflash memory, a read-only memory (ROM), and/or a random-access memory(RAM). As used herein, the term tangible computer readable medium isexpressly defined to include any type of computer readable storage andto exclude propagating signals. Additionally or alternatively, theexample processes of FIGS. 22-24 may be implemented using codedinstructions (e.g., computer readable instructions) stored on anon-transitory computer readable medium such as a flash memory, aread-only memory (ROM), a random-access memory (RAM), a cache, or anyother storage media in which information is stored for any duration(e.g., for extended time periods, permanently, brief instances, fortemporarily buffering, and/or for caching of the information). As usedherein, the term non-transitory computer readable medium is expresslydefined to include any type of computer readable medium and to excludepropagating signals.

Alternatively, some or all of the example processes of FIGS. 22-24 maybe implemented using any combination(s) of application specificintegrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)),field programmable logic device(s) (FPLD(s)), discrete logic, hardware,firmware, etc. Also, some or all of the example processes of FIGS. 22-24may be implemented manually or as any combination(s) of any of theforegoing techniques, for example, any combination of firmware,software, discrete logic and/or hardware. Further, although the exampleprocesses of FIGS. 22-24 are described with reference to the flowdiagrams of FIGS. 22-24 , other methods of implementing the processes ofFIGS. 22-24 may be employed. For example, the order of execution of theblocks may be changed, and/or some of the blocks described may bechanged, eliminated, sub-divided, or combined. Additionally, any or allof the example processes of FIGS. 22-24 may be performed sequentiallyand/or in parallel by, for example, separate processing threads,processors, devices, discrete logic, circuits, etc.

FIG. 22 provides a flow diagram 2200 for a method for donor access toblood collection information. At block 2210, a donor accesses bloodcollection information via a mobile device. The donor can be providedwith a variety of information and functionality, such as facilitylocation, donation information, educational resources, etc. At block2220, the donor selects an available option. At block 2230, the donorviews his or her donation information via the mobile device. At block2240, the donor locates a donation facility via the mobile device. Atblock 2250, the donor accesses training/educational materials via themobile device.

At block 2260, selected content is displayed to the donor via the mobiledevice. For example, donation information is shown, a donation facilityis mapped, and/or educational materials are displayed for review and/orinteraction. At block 2270, the donor can interact with the displayedcontent. At block 2280, based on the interaction, an output is providedfrom the mobile device. For example, donation information can beupdated, an appointment can be made, results can be sent, etc. Themethod can be executed in accordance with many examples, includingexamples described above.

FIG. 23 provides a flow diagram 2300 for a method for operator access toblood collection information. At block 2310, an operator accesses bloodcollection instrument information via a mobile device. At block 2320,blood instrument information is retrieved for operator review at themobile device. At block 2330, the operator can review and/ortroubleshoot the instrument via the mobile device. At block 2340, theoperator can interact with the instrument via the mobile device. Atblock 2350, the mobile device provides an output based on the operatorinteraction with the instruction. The method can be executed inaccordance with many examples, including examples described above.

FIG. 24 provides a flow diagram 2400 for a method for administratoraccess to blood collection information. At block 2410, an administratoraccesses blood collection facility information via a mobile device. Atblock 2420, blood collection facility and/or instrument information isretrieved for administrator review via the mobile device. At block 2430,the administrator can perform a variety of activities, such astroubleshooting, scheduling, etc., with respect to one or more bloodcollection instruments in the facility. At block 2440, the administratorcan interact with the one or more instruments via the mobile device. Atblock 2450, the mobile device provides an output based on theadministrator interaction with the facility. The method can be executedin accordance with many examples, including examples described above.

Bar Code Data Bridge

FIG. 25 relates to a bar code data bridge. The bar code data bridge canbe used in conjunction with a mobile computing device, such as aniPhone™, iPad™, BlackBerry™, Android phone, etc., with a scanner orcamera to capture the bar code information. The bar code data bridge canoperate in conjunction with a donor, operator, and/or administratorapplication or interface as described above.

In some examples, a “Transition Label” for blood containers may containboth Codabar and ISBT 128 bar codes to meet the needs of U.S. bloodcenters during the industry's conversion from Codabar to ISBT 128labeling standards. Many data management software packages are currentlydesigned to use Codabar bar code information and are not yet able tointerpret the ISBT128 Manufacturer's Data Files that provide certainprocess control information for the blood centers. In some cases,providers may decide to convert to “full format” ISBT 128 labels withoutthe Codabar information. If this occurs before data management softwareis updated to utilize the ISBT 128 data files, blood centers may losecertain process control information on the labels. U.S. Pat. No.7,588,193, incorporated by reference herein in its entirety, is co-ownedwith the present application by Fenwal, Inc., and provides example of ablood component container label including at least one bar code based ona first bar code format and another bar code based on a second bar codeformat.

In some examples, handheld personal digital assistants (PDAs) (e.g.,iPhone™, etc.) with bar code scanners are utilized to decode ISBT 128bar codes and display important process control information for the setthat is contained within ISBT 128 Manufacturer's Data Files that areelectronically distributed by the blood bag manufacturers.

In some examples, the donor ID bar code is scanned from donorregistration paperwork to access database of donor history. For example,the PDA can be loaded with a database of donor records.

In some examples, an electronic donation record is created and/or bloodbag and/or kit bar codes to record code, lot, and/or other informationis scanned.

In some examples, a PDA is connected to a computer to transmit donationrecords to a component processing lab.

In certain examples, a PDA can be connected to one or more smallportable printers to print ISBT 128 blood product code labels on demand(e.g., the PDA is loaded with a database of ISBT 128 product codes usedby the blood center), for example.

In some examples, a software patch may be provided to link the GTIN (GS1 Global Trade Item Number) contained in the ISBT 128 Manufacturer'sData Files to inventory control systems to trigger new orders of SPUs orkits when supplies are low.

In some examples, the application reduces or minimizes paperwork anderrors at the blood collection center, and helps identify new candidatesfor automated procedures based on donor history.

In some examples, the application helps improve labor efficiency at thecomponent processing lab and automates the reconciliation process forincoming products.

In some examples, the application reduces or minimizes the amount ofdiscarded blood products that are not processed within the allowabletimeframe.

In some examples, the application reduces or minimizes label inventoryand scrap for preprinted ISBT 128 product codes at the componentprocessing lab.

In some examples, the application helps improve patient safety bypreventing component processing errors.

In some examples, the application helps prevent blood processing unit(BPU)/kit inventory stock-outs at blood centers.

The application may include an over-labeling aspect of the process. Insome examples, the application may include different scanning points(e.g., at cooler/truck/centrifuge).

In some examples, the product bar codes may no longer be on the baselabel because the use of the manufacture's data files may eliminate aneed for the product bar codes.

As shown in FIG. 25 , a process flow 2500 demonstrates how bloodproducts can be processed and labeled with new product codes. At 2510, ablood center downloads one or more manufacturer data files (MDFs) (e.g.,ISBT 128 manufacturer data files) from a blood bag manufacturer'swebsite. At 2520, an MDF and a database of blood product codes used bythe blood center are transmitted to a mobile computing device. Incertain examples, donor history and/or recommended procedures (e.g., forthe particular donor, desired inventory, etc.) are transmitted as well.

At 2530, bar codes (e.g., donor identification and blood bag bar codes)are scanned at a time of blood collection. A donation record is enteredelectronically. A donor history may be reviewed as well, for example. At2540, donation record(s) are electronically transmitted and bloodunit(s) are transported to a component production laboratory, forexample.

At 2550, the component production lab scans the donor identificationnumber on each bag to reconcile each unit against the donationrecord(s). At 2560, the component production lab scans the manufacturercatalog number bar code (e.g., ISBT 128) to access container informationprovided in the MDF (e.g., the ISBT 128 MDF).

At 2570, the mobile computing device displays a list of pre-loaded bloodproduct code(s) approved for storage in the selected container. Theoperator selects a product code and prints an overlabel (e.g., an ISBT128 overlabel), for example. At 2580, blood product(s) are processed andlabeled with the new product code.

FIG. 26 is a block diagram of an example system or mobile device 3600including an application 3602, an interface 2604 including a sensor(s)2606, a processor 2608 and a data store 2610. The example system 2600may be used to implement the example mobile devices described above, forexample. While an example manner of implementing the mobile device 100,600, 700, 900, 1200, 1300, 2100, etc., has been illustrated in FIG. 26 ,one or more of the elements, processes and/or devices illustrated inFIG. 26 may be combined, divided, re-arranged, omitted, eliminatedand/or implemented in other ways.

The application 2602, the interface 2604, the sensor 2606, the processor2608 and/or the data store 2610 and, more generally, the example system2600 may be implemented by hardware, software, firmware and/or acombination of hardware, software and/or firmware. Thus, the application2602, the interface 2604, the sensor 2606, the processor 2608 and/or thedata store 2610 and, more generally, the example system 2600 can beimplemented by one or more circuit(s), programmable processor(s),application specific integrated circuit(s) (ASIC(s)), programmable logicdevice(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)),etc. When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the application 2602,the interface 2604, the sensor 2606, the processor 2608 and/or the datastore 2610 and, more generally, the example system 2600 are herebyexpressly defined to include a tangible medium such as a memory, DVD,CD, Blu-ray, etc., storing the software and/or firmware. Further still,the example system 2600 of FIG. 26 may include one or more elements,processes and/or devices in addition to, or instead of, thoseillustrated in FIG. 26 , and/or may include more than one of any or allof the illustrated elements, processes and devices.

The application 2602 may include instructions that, when driven by theprocessor 2608, cause the processor 2608 to retrieve data, tutorialinformation, audio, graphics, text, etc. and display the same using theinterface 2604. For example, based on the initiation of a tutorialsession, the application 2602 may cause a video to be displayed on theinterface 2604 on how to operate and/or troubleshoot a blood processinginstrument. The application 2602 may cause instructions to be displayedon the interface 2604 on how to participate in the tutorial. In someexamples, based on the system 2600 identifying the user's experiencelevel, a different tutorial and/or information may be displayed. Thesystem 2600 may identify the user's experience level from data stored atthe data store 2610 and/or based on input received from the user.

Based on the information received, the processor 2608 may generatefeedback that may be displayed at the interface 2604 and/or stored atthe data store 2610. Once the processor 2608 determines that thetutorial is complete, the processor 2608 may generate feedback relatingto the user's performance, etc. While the data store 2610 is depicted asbeing within the system 2600, the data store 2610 may be at a differentlocation (e.g., a remote location).

The processor 2608 may drive the interface 2604 to provide informationand/or functionality to the user. In some examples, the interface 2604may be configured as a graphical user interface (GUI). The GUI may betouch pad/screen integrated with the system 2600. The system 2600 mayinclude one or more internal memories and/or data stores including thedata store 2610. Data storage can include any variety of internal and/orexternal memory, disk, remote storage communicating with the system2600.

FIG. 27 is a block diagram of an example processor system 2700 that canbe used to pump, implement, control and/or drive the systems and methodsdescribed herein. As shown in FIG. 27 , the processor system 2700includes a processor 2702 that is coupled to an interconnection bus2704. The processor 2702 may be any suitable processor, processing unitor microprocessor. Although not shown in FIG. 27 , the processor system2700 may be a multi-processor system and, thus, may include one or moreadditional processors that are identical or similar to the processor2702 and that are communicatively coupled to the interconnection bus2704.

The processor 2702 of FIG. 27 is coupled to a chipset 2706, whichincludes a memory controller 2708 and an input/output (I/O) controller2710. As is well known, a chipset typically provides I/O and memorymanagement functions as well as a plurality of general purpose and/orspecial purpose registers, timers, etc. that are accessible or used byone or more processors coupled to the chipset 2706. The memorycontroller 2708 performs functions that enable the processor 2702 (orprocessors if there are multiple processors) to access a system memory2712 and a mass storage memory 2714.

The system memory 2712 may include any desired type of volatile and/ornon-volatile memory such as, for example, static random access memory(SRAM), dynamic random access memory (DRAM), flash memory, read-onlymemory (ROM), etc. The mass storage memory 2714 may include any desiredtype of mass storage device including hard disk drives, optical drives,tape storage devices, etc.

The I/O controller 2710 performs functions that enable the processor2702 to communicate with peripheral input/output (I/O) devices 2716 and2718 and a network interface 2720 via an I/O bus 2722. The I/O devices2716 and 2718 may be any desired type of I/O device such as, forexample, a keyboard, a video display or monitor, a mouse, etc. Thenetwork interface 2720 may be, for example, an Ethernet device, anasynchronous transfer mode (ATM) device, an 802.11 device, a DSL modem,a cable modem, a cellular modem, etc. that enables the processor system2700 to communicate with another processor system.

While the memory controller 2708 and the I/O controller 2710 aredepicted in FIG. 27 as separate blocks within the chipset 2706, thefunctions performed by these blocks may be integrated within a singlesemiconductor circuit or may be implemented using two or more separateintegrated circuits.

Certain examples can include processes that can be implemented using,for example, computer readable instructions that can be used tofacilitate mobile blood applications for donors, operators,administrators, and/or providers. The example processes can be performedusing a processor, a controller and/or any other suitable processingdevice. For example, the example processes can be implemented usingcoded instructions (e.g., computer readable instructions) stored on atangible computer readable medium such as a flash memory, a read-onlymemory (ROM), and/or a random-access memory (RAM). As used herein, theterm tangible computer readable medium is expressly defined to includeany type of computer readable storage and to exclude propagatingsignals. Additionally or alternatively, the example processes can beimplemented using coded instructions (e.g., computer readableinstructions) stored on a non-transitory computer readable medium suchas a flash memory, a read-only memory (ROM), a random-access memory(RAM), a CD, a DVD, a Blu-ray, a cache, or any other storage media inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, brief instances, for temporarily buffering, and/orfor caching of the information). As used herein, the term non-transitorycomputer readable medium is expressly defined to include any type ofcomputer readable medium and to exclude propagating signals.

Alternatively, some or all of the example processes can be implementedusing any combination(s) of application specific integrated circuit(s)(ASIC(s)), programmable logic device(s) (PLD(s)), field programmablelogic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc.Also, some or all of the example processes can be implemented manuallyor as any combination(s) of any of the foregoing techniques, forexample, any combination of firmware, software, discrete logic and/orhardware. Further, although example processes may be described withreference to a particular order and/or structure, other methods ofimplementing the processes may be employed. For example, the order ofexecution of the blocks can be changed, and/or some of the blocksdescribed may be changed, eliminated, sub-divided, or combined.Additionally, any or all of the example processes can be performedsequentially and/or in parallel by, for example, separate processingthreads, processors, devices, discrete logic, circuits, etc.

While particular embodiments of the invention have been shown anddescribed, it will be obvious to those skilled in the art that changesand modifications may be made therein without departing from theinvention in its broader aspects.

What is claimed is:
 1. A system for collecting whole blood from blooddonors and monitoring donation information on a handheld computingdevice, comprising: first whole blood collection devices disposed at afirst blood donation center and configured to collect whole blood fromdonors, wherein the first blood donation center is a mobile collectionsite; second whole blood collection devices at a second blood donationcenter which is different than the first blood donation center; ahandheld computing device comprising a housing, a touch screen displaycoupled to the housing, a memory to store an executable application, anetwork interface circuit configured to communicate wirelessly, and aprocessing circuit coupled to the display, the network interface circuitand the memory, wherein the handheld computing device is configured toretrieve a location of the first blood donation center; a remote servercomputer in wireless communication with the first and second whole bloodcollection devices and the handheld computing device, wherein the firstand second whole blood collection devices are each configured totransfer donation procedure information to the remote server using atleast one communication protocol, wherein the remote server computer isconfigured to facilitate retrieval of the donation procedure informationat the handheld computing device; wherein the donation procedureinformation comprises data based on product volume collected; whereinthe donation procedure information comprises facility information;wherein the handheld computing device is configured to display a numberof whole blood units collected; and wherein the donation procedureinformation comprises data indicating performance of operators of thefirst and second whole blood collection devices.
 2. The system of claim1, wherein the data indicating performance of operators of the wholeblood collection devices comprises a real time scoreboard or scorecard.3. The system of claim 2, wherein the handheld computing device isconfigured to generate feedback relating to the performance of theoperators.
 4. The system of claim 1, wherein the handheld computingdevice is configured to receive user selection of one or more donationlocations and to display donation records comprising quantity of blooddonations at the one or more donation locations.
 5. The system of claim1, wherein the handheld computing device keeps track of progress ofdonations.
 6. The system of claim 1, wherein the first and second wholeblood collection devices are configured to generate electronic donationrecords, wherein the donation procedure information comprises theelectronic donation records.
 7. The system of claim 1, wherein thedonation procedure information comprises donation statistics.
 8. Thesystem of claim 1, wherein the number of whole blood units collectedfurther comprises a current number of whole blood units collected byeach of the first and second blood donation centers.
 9. The system ofclaim 1, wherein the handheld computing device is configured to retrievefrom the first and second whole blood collection devices for displayfacility information for the first and second blood donation centers.10. The system of claim 1, wherein the handheld computing device isconfigured to display the number of whole blood units collected by eachof the first and second blood donation centers.
 11. The system of claim1, wherein the remote server is configured to provide username andpassword access to an administrator to log into an account on a websiteoperated by the remote server.
 12. A system for collecting whole bloodfrom blood donors and monitoring donation information on a handheldcomputing device, comprising: whole blood collection devices disposed ata blood donation center and configured to collect whole blood fromdonors, wherein the blood donation center is a mobile collection site; ahandheld computing device comprising a housing, a touch screen displaycoupled to the housing, a memory to store an executable application, anetwork interface circuit configured to communicate wirelessly, and aprocessing circuit coupled to the display, the network interface circuitand the memory; v a remote server computer in communication with thewhole blood collection devices and the handheld computing device,wherein the whole blood collection devices are each configured totransfer donation procedure information to the remote server, whereinthe remote server computer is configured to facilitate retrieval of thedonation procedure information at the handheld computing device; whereinthe procedure information comprises data based on product volumecollected; wherein the handheld computing device is configured toretrieve a location of the blood donation center; wherein the handheldcomputing device is configured to display a number of whole blood unitscollected; wherein the donation procedure information comprises dataindicating performance of operators of the whole blood collectiondevices; and wherein the data indicating performance of operators of thewhole blood collection devices comprises a real time scoreboard orscorecard.
 13. The system of claim 12, wherein the handheld computingdevice is configured to generate feedback relating to the performance ofthe operators.
 14. A method of collecting whole blood from blood donors,comprising: collecting whole blood from donors using first whole bloodcollection devices at a first blood donation center; collecting wholeblood from donors using second whole blood collection devices at asecond blood donation center which is different than the first blooddonation center; providing a handheld computing device comprising ahousing; providing a remote server computer in wireless communicationwith the first and second whole blood collection devices and thehandheld computing device, transferring donation procedure informationfrom the first and second whole blood collection devices relating to thecollections of whole blood to the remote server computer using at leastone communication protocol; facilitating retrieval of the donationprocedure information by the handheld computing device from the remoteserver computer, wherein the retrieved donation procedure informationcomprises data based on product volume collected and data indicatingperformance of operators of the first and second whole blood collectiondevice; displaying on the handheld computing device a number of wholeblood units collected; and generating feedback relating to theperformance of the operators on the handheld computing device, wherebyblood collection can be improved.
 15. The method of claim 14, whereinthe data indicating performance of operators of the first and secondwhole blood collection devices comprises a real time scoreboard orscorecard.
 16. The method of claim 14, further comprising receiving oneor more donation locations at the handheld computing device anddisplaying donation records comprising quantity of blood donations atthe one or more donation locations.
 17. The method of claim 14, furthercomprising displaying donation statistics on the handheld computingdevice.
 18. The method of claim 14, further comprising using thefeedback to provide user training with respect to blood collectionprocedures.